• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    A system and method for collecting and managing within-page components and component collections. The invention allows users to identify components within a document which they wish to gather together int o a collection. Once the components are identified, a tool lets users automatically gather the identified components into a new document. The components in the new document automatically include an identifying header as well as a hyperlink back to that source document. The collection of identified components may be edited and shared.
    公开号:CA2397873A1
    申请号:C002397873
    申请日:2002-08-12
    公开日:2003-02-13
    发明作者:Monica M. C. Schraefel
    申请人:Monica M. C. Schraefel；
    IPC主号:G06F16-93
    专利说明:
    [1" class="description-paragraph] Bereskin & Parr CANADA B&P Reference No: 2223-151 Patent Application Title: System and Method for Collecting and Managing Within-Page Components and Component Collections Inventor(s): monica c. schraefel Tit1 ' m n r II 'n n i en an~om~onent C~Ilections Field of the Invention (0001] This invention relates a system and method for making and managing collections of smaller-than-page-sized information components within documents.Background of the Invention
    [2" class="description-paragraph] (0002] To efficiently utilized information, it is generally necessary to be able to organize the information, or more commonly a subset of it, for simple and easy retrieval. In the context of information available on computer systems such as the Internet, there are two main organizational methods: editors and bookmarks.
    [3" class="description-paragraph] (0003] Editors. There are several applications which let users paste material copied from one document into this other. Examples are simple text editors (vi on Unix, Notepad on Windows, SimpIeText on MacOS), complete word processors, or web-page building applications such as Microsoft FrontPage or Netscape Communicator. Front Page and Communicator are separate applications which cooperate with a web browser to let users copy content from web pages into them.They are different from text editors and word processors in that they maintain original web page elements like font size and type face. These tools, however, do not maintain links with source documents, nor do they provide automatic captioning for identifying information about the copied component. Similarly, they create static, local collections:once the material is copied from the web page, it has no connection back to the source document. If the source is changed, the copied material is out of sync with that originating document. Similarly, the programs that create these files require that if the user wants to store the file on a network to be accessed remotely, the user must have such a storage location for their Piles.
    [4" class="description-paragraph] [0004] Bookmark Tools. Bookmarking tools let a user create a collection (list) of hyperlinked references to an entire "page" or document of information. A bookmark, a single reference within this list, refers to what we call "whole page representation."
    [5" class="description-paragraph] [0005] Bookmark Tools. The most transparent mechanism available for creating Web references is the browser bookmark function, which captures the URLof an entire page. There are a variety of bookmark tools available from the generic browser-based bookmark tool, to stand alone applications that work with browsers to track or visualize pages in a collection. In each case, however, the entire page is captured as part of a list of a larger collection of previously collected pages. List manager tools such as these also require that a user reopen each page to get at the bookmarked pages.
    [6" class="description-paragraph] [0006] Guide Tools and Spatial Hypermedia. Within the hypermedia community, there are models for creating one's own link paths through a set of documents.Walden's Paths is a Web-based embodiment of such a tool. User-defined paths can then be shared with others. Walden's Paths, however, represents whole pages only, rather than components of a page. As well, collections do not by default imply a specific traversal among the gathered pages; indeed, in most cases they would resist such ordering.
    [7" class="description-paragraph] [0007] Unlike Walden's Paths explicit traversal semantics, Web Squirrel, a commercial, platform-specific, stand alone tool for URL management, is based on spatial hypermedia work. This approach represents data as visual objects to be directly manipulated in a 2D space. In this case, page titles, dragged and dropped from Web page URLs, appear as boxes on a plane. The objects can then be arranged or grouped in any configuration and annotated. Agents can sift through annotations or other information and suggest connections among collected objects. In these respects, Web Squirrel presents a fast visual overview of topics in a collection. Other research in bookmark collecting has also demonstrated the value of being able to arrange bookmarks visually, both for communicating information about the collection, and for recalling the information about specific components in a collection. However, like pages referenced by bookmarks, the annotation/link information attached to Web Squirrel boxes is hidden from view. Only one box's information can be revealed at a _2_ time. As well, if a user cuts and pastes, or drags and drops text information from a Web page into Web Squirrel, the source URL for that text is lost unless the user also grabs the URL and drops that into the application. This URL will then show up as a distinct box from the text. Finally, Web Squirrel does not capture images or other media.
    [8" class="description-paragraph] [0008) One other now-famous representation of Web documents within a spatial context is Xerox's WebBooks. In this case once again whole pages are represented. Collections of pages are visualized as books, where pages in the collection can be "flipped" through quickly. Not unlike Walden's Paths, an order through which the pages can be viewed is implied by the order the pages are represented in a WebBook. This metaphor may, therefore, be too structured for the more heterogeneous, non-linear aspect of within-page component collections.
    [9" class="description-paragraph] (0009) Tool Assessment In summary, existing tools for collection activity are largely versions of bookmark tools, and, as such, are biased for whole page collection and management. Bookmark tools, however, make it easy for users to capture page references transparently without forcing divided attention. Browser-based editors are more flexible than bookmark applications both in the kinds of information they can capture and in the way that information is represented in a page (users can see all the content in a file; they cannot see the content in a list of bookmarks). The editors, however, lack the automatic referencing of bookmarks, and the automatic currency of the document being represented by the reference. As a special case of bookmarks, super bookmarks let users create collections of previously made, individual bookmarks with anchors. This, however, requires a two step process for users interested in making collections in the first place, such they must first create a series of bookmarks and then group these into collections, and create yet another bookmark for this collection.Summary of the Invention
    [10" class="description-paragraph] (0010] The system and method of the present invention have several related parts. The invention allows users to identify components within a document which they wish to gather together into collection; once identified, the tool lets users automatically have the identified components gathered into a new document. The components in the new document automatically include an identifying header (such as the name of the component's source document) as well as a hyperlink back to that source document.
    [11" class="description-paragraph] [0011] Hyperlinks and hypermedia systems provide the ability to connect distinct entities across a local system (like the files on one's personal computer) or across a network. The World Wide Web (WWW or Web) (which is part of the Internet) is only one example of a hypermedia system.
    [12" class="description-paragraph] [0012] Distinctness: Our tool is distinct from bookmarks because it focuses on supporting the capture/referencing of smaller-than-whole-page entities (components) as collections. It lets users capture such within-page components. Our tool is distinct from text editors because it does not copy the selected content of a source document, but rather stores a reference (address) for each component collected. With the present invention, the user can go from page to page, identifying areas of a document they wish to be "collected." This action creates a Collection List. This Collection List of component references is then processed (which we call "rendered"), at the user's request, so that the most current version of each of the listed components is displayed in a new document. The user can then perform a variety of operations on the collected components, such as renaming them, sorting or deleting them. Users can also rename the title for their collection. These changes are automatically stored. A user can then save the hyperlink which represents the collection they have just made. This link can be given to anyone else who has access to the user's network or local system so that they can re-render the collection for themselves.
    [13" class="description-paragraph] [0013] Components in this tool. It is important to make a distinction between (1 ) how our tool references components and (2) the Dexter and Open Hypermedia Systems Working Group (OHSWG) models of components in Open Hypermedia Systems. Dexter and OHSWG refer to components as abstract data types for representing link and information data as hypermedia objects. In this paper, the term "component" refers simply to an information unit within a document.
    [14" class="description-paragraph] [0014] Our tool supports (i) transparent component capture (or collection), where these components, once selected, can be placed in a new document without the user needing to manage the process (ii) automatic component labeling for later reference in a new context (iii) component-source retrieval, so that a user of the new collection can easily recover the original source/context of the component.
    [15" class="description-paragraph] [0015]Brief Description of the Drawings
    [16" class="description-paragraph] [0016] An embodiment of the present invention will now be described, by way of example only, with reference to the drawings, in which:Figure 1 is a flow chart that represents (I) component selection of within-page components for collection, (II) the process of creating the rendered collection, and (III) the actions available for editing the collection. The process is iterative: the user may add a component, render or edit a collection at any time in the cycle. Numbers 1 to 14 in Figure 1 represent the individual steps within this selection of components for a collection, rendering the view of the collection, editing the collected elements of a collection.Figure 2A represents one way to view and edit a collection: as a list of references (component titles) that are added to the Collection List each time a user selects a component to add to a collection. Figure 2A Parts 1 to 8 represent elements in the list and how they can be edited, sorted or deleted.Figures 2B and 2C below show one way to edit component names and a name for the collection itself in the list view that represents the collection.Figure 3 is a partial view of a collection which a user can scroll through. Figure 3 Parts 1 to 4 identify components of this Collection View.Figures 4A, 4B, 4C show one way of indicating several elements for collections by having the elements available for collection. Figure 5 indicates another way of indicating the selection of an element for collection. Figures 6A and 6B show prior art for representing URLs and document elements. Figures 7A and 7B show the manner of URLs designed for collection purposes. Figure 8 shows the architecture diagram for the current preferred embodiment of creating collections for within-page-components.Detailed Description of a Preferred Embodiment
    [17" class="description-paragraph] [0017] An exemplary web-based embodiment of the present invention is described here. This embodiment is also Java and XML-based. The invention is not limited to use on the Web, Java or XML. The architecture of the exemplary embodiment is shown in Figure 8.Hunting, Gathering and Pout processing Overview
    [18" class="description-paragraph] [0018] To support our design specifications within a Web-based world, and without requiring a stand alone application, this exemplary embodiment of the collection-making tool is XML-based system to take advantage of XML's properties for accessing document structure. We also implemented our system with Java. Other systems, such as SGML, with other programming languages, could be used as well for both web and non-web-based applications. We use a combination of client side and server side processes in the tool architecture. The client server model we have implemented works over a network, specifically the Internet, but could just as readily work on an individual's non-networked computing device, or across any file structure system. In the current preferred embodiment architecture, there are five main steps:(1) support the selection of user-identified components in a document as per Fig 1, element 2; (2) create a reference for that component, as per Fig 1, part I, 4; (3) add that component to a list of existing components or start a new list if none exists, as per Fig 1, I part 5 (4) render a page that contains these components along with the link of the source document of each component, and title for each component as per Fig 1, II part 10 and as exemplified in Fig 3 part A and B and C; (5) facilitate the user's sorting, deleting or addition of current components within the collection, as per Fig 1, III, and as exemplified in one embodiment in Fig 2.
    [19" class="description-paragraph] [0019] Preparation for Page Processing. This embodiment uses the markup of a document in order to locate elements within that document. The markup in a word processing document which indicates things like paragraph breaks and tab stops is usually in a different language than the markup used to create these effects in web pages, but the role of markup serves the same purpose in each. Our tool's preferred embodiment processes a document's markup through a technology known as Extensible Markup Language (XML). XML is an open standard and has processes for treating document markup in a structured way, like a tree structure. By moving through the tree from its root, we can locate elements in the markup. We use this process to support a user's identification of a component in a document page they wish to collect. The system matches the user's selection with the appropriate component which is used to create an address for that component location, something like:This.document. root/3stepsdownfromtheroot.
    [20" class="description-paragraph] [0020] We can use a variety of methods supported in browsers and XMLprocesses, such as XPath and XPointer to locate selections within a document element (like the third word in the third sentence of a paragraph element) or to select multiple whole elements (like several paragraphs and a header) in a page.
    [21" class="description-paragraph] [0021] A collection list (such as that embodied in Figure 2A) is made up of these component addresses, which we describe below in the section on AURLs. In the Collection List, only the text name of the source document (which is editable by the user) is shown (Figure 2A, part 7), rather than the URL file system address for the element. In this embodiment, the URL is only shown in the rendered version of the list, as in Fig 3, part 3. Any variety of ways to represent the name/address of the component in the collection is possible.
    [22" class="description-paragraph] [0022] Specifics. In this web-based embodiment of the invention, we convert web-based files to be accessed by the tool(marked up in HTML) into XHTML files.XHTML is an XML language. XHTML pages can be a) viewed in a browser like regular web pages and b) can be treated like XML pages (which HTML pages cannot: raw _7_ HTML has no way to speak to the XML processes). That is, once the pages are in XHTML form, their document structure can be addressed. We can create references for the different parts in the document. The only software required for this structure/display markup is a browser which can interpret XHTML source files, which is currently just about all version 5 browsers and above. This same process, however, could be applied over documents on a user's local file system. One way would be to have a local application which can convert the markup language of a given document into XML coordinates which can be added to a similar document component list and then rendered in a new document. Such a system would allow users of local or remote files to create collections of heterogeneous document components, easily taking them back to the source document, should they need to do so.
    [23" class="description-paragraph] [0023] In this web-based embodiment, we convert the files with a server-side process: if the source file is XML, we run an XML parser to convert the file, since raw XML cannot be displayed in a browser. If the source file is HTML, we run the free-source application HTML Tidy to prepare an appropriate XHTML file to be XMLcompliant. The next step is to add a reference to a file that will do the processing of the components identified for collection. In this embodiment, this header markup is done by a proxy service, but in an alternative embodiment it could be done by a browser-based plug-in or other mechanism. The important point to note is that there need to be mechanisms to connect the user's selection in a window of a component to be addressed with a system able to translate that selection in the window with the (invisible to the user) markup in the document. In our case, we are able to match a compliant browser's support for the Selection Object of the Document Object Model of the World Wide Web Consortium (an open protocol) with XML's XPath processes.This lets what the user selects in the window be coordinated with the correct location in the document.~ http://www.w3.org/People/Raggett/tidy/_g_ Component Identification.
    [24" class="description-paragraph] [0024] Components are addressed by their markup. For example, in the XHTMLpage source, a paragraph of text might be indicated by being enclosed by <p>... <1p>, or, if the content is inside a table, by <td>... </td>. While these different tags may affect the look of the page to a user, they are treated the same way by the system: they act as an address to indicate a location in the document where content exists.Selectable Component Indication. In the present embodiment, there are two ways that an element can currently be identified for collection. First, if a user holds down the control key on their keyboard, and rolls the mouse over the page, they will see boxes appear around parts of the page as they scroll over them as shown in Figures 4A, 4Band 4C. These boxes or borders indicate the page elements that are collectible. Auser can collect either ONE element at a time (Figures 4A and 4B), or by holding down the control and shift keys, they can collect contiguous elements (Figure 4C). These contiguous elements will be collected as a group, and treated as a unit (given one address) in the collection list (as per the first title listed in the Collection List in Figure 2A). A second way to collect elements is to use the mouse to highlight a part of the document to be collected, as shown in Figure 5, part 1. Any other method of identifying an element for collection may also be used.
    [25" class="description-paragraph] [0025] In both cases, after the areas have been selected for collection, users hit the "a" key, and a dialog box pops up to ask them if they wish to add an element to a collection, as per Figure 5, part 2.
    [26" class="description-paragraph] [0026] The user can gather more elements from that page (as Figures 4A, 4Band 4C demonstrate), or move to a new page and collect elements from the new page.
    [27" class="description-paragraph] [0027] As shown in the flowchart in Figure 1, at any time in this selection/collection process, the user may render the collection in Collection View. In this web-based embodiment, the Collection View constitutes a new web page which is represented by the URL for the collection. In the next section, we describe in detail how the system knows which components to render in the page. Aggregated URLs (AURLs)
    [28" class="description-paragraph] [0028] In this exemplary embodiment, we use XML's XPath2 to process client requests to add components to collections. When a user selects a Web page component, the client sends a request with the parameter "AURL" to a server. The AURL is composed of three parts: an XPath, a text Title value from the page of the component selected, and the identifier of the component selected. For example, a component from a web page may be represented by the following HURL"http://dgp.toronto.edu/fred2.html#html//div[@id='undergrad']#m.c. schraefel, ut, cs, current courses"
    [29" class="description-paragraph] [0029] Here, #htmt//div[(c,~id='undergrad'] is used by XPath and the string following "#" is the component's title, which will be used in the collection page for labeling the component. When the server accepts the request, it first gets the session that is associated with the request. If it is the first request of the client to select a component, the server will create a new Collection session. The server then stores the current AURL or appends the new AURL to the existing AURL for this session. For example, a complete Collection URL with three components from the collection in Figures 2A and 4 looks like this:http :I/atlas.dgp.toronto.edu:8080/exam Ies/servlet/Collection b aurl=htt %3a%2f 2fwww%2edgp%2etoronto%2eedu°~2f%257Emc%2fpagers2%2ehtm~%23DIV%232%231 %23m.c.%20schraefel,%20selected%20~apers /o7chttp %3a%2f%2fww w%2ecdf%2etOronto%2eedu%2f%7ecsG428h%2f /o23P%231 %232%23csc428:%20Human%20Computer%201nteraction%2011%7chttp%3a%2f%2fwww%2ecdf%2e toronto%2eedu%2f%257Ecsc318h%2f318project2000%2ehtml%23%23assignX23L1%239%233%233183/o20Project%202001 %20due%20dates&pagetitle=schr aefel%20courses+related 2 XSLT and XPath are part of the Extensible Stylesheet Language (XSL) specification for XML. XSL consists of three parts: the XSL language specification, XSL Transformations (XSLT), and XML Path Language (XPath). The XPath language is used to locate certain parts of an XML document. It is meant to be used by an XSLT stylesheet, but we use it here in our Collection server for parsing the AURL in order to avoid lengthy iteration over a DOM(Document Object Model) element hierarchy.The Collection URL is compatible with the URI specification, as par http://www.ietf.org/rfc/rfc2396.txt.
    [30" class="description-paragraph] [0030] The first part of the URL is the address of the Collection server. After the " " the list includes what we call an AURL, or "Aggregate URL" that consists of the collected components ids and source URLs.4
    [31" class="description-paragraph] [0031] The server does not store the components for a collection; it renders the collection from the list of components in the Collection URL. This makes collections highly portable as sharable URLs, since URLs are simply text strings referencing a document. In our case, the AURL represents a composite of components from various pages also represented by URLs. If components are added or changed in a collection, a new AURL is created by default, which makes version control a side-effect of the process: one can non-destructively re-render alternate or previous versions of a collection via the AURL created for each version.
    [32" class="description-paragraph] [0032] AURLs are based on URLs developed in Intensional HTML (IHTML) by one of the applicants for version control. In IHTML, users can configure page level components through the selection of parameter values available in a page. For instance, one component can be set to Student view, level of detail Light, and another component to Professor view, level of detail Medium. The entire page may be set to Language, French. URLs are used to store state of page by placing parameter into the URL, and using that both to store the state of the current page in a bookmark, or maintain the state of dimensions (such as language or font) across pages accessed in the site We have adopted the IHTML URL model for Collection URLs and their AURL component references.
    [33" class="description-paragraph] [0033] Also, while the AURL is an efficient and versatile way to indicate collections, since it can be readily bookmarked or emailed as text to a user, and requires no special storage or application, the URLs can get long. It would be possible to create a unique identifier for the AURL that would be shorter and would point to the full URL when the alias for the URL is referenced in a browser.
    [34" class="description-paragraph] [0034] Another potential advantage of AURLs is that since they reference rather than store components, they always return the most current version of a given page element. This means, in pages where current information is critical, from exam 4 AURLs are informed by use of URLs to store page version information in adaptable Web pages, as per [20]. schedule information to team scores, the information returned each time the collection page is accessed is current. There will no doubt be times when users wish to take a snap shot of a collection's data at a specii:lc instance rather than rendering only the most current version of the components. We are investigating ways to make such pages simple to indicate and store, for instance, to a user's networked disk so users can continue to access their collections from remote locations. Collection Pages and Collection Management
    [35" class="description-paragraph] [0035] In the present embodiment, a collection may be represented in two ways: a Collection List view (Figure ZA) and a Collection view (Figure 3).
    [36" class="description-paragraph] [0036] Collection List View. This View first appears when users initiate a collection session. When a component reference is processed by the server, the user is presented with a page that lists the components selected (Figure 2A). As a default, the list consists of the Title values from the components' source pages (Figure 2A, part 7). If a title exists for the element itself in a document, the element title will be used rather than the document title. In the collection process, new titles are added to the list, as per Figure 1, I part 5. While the collection is being made, the System keeps track of references being added to it: it passes new components back to the list to update the Collection List.
    [37" class="description-paragraph] [0037] Titles, once clicked on by the user, can be sorted up or down (Figure 2A, parts 1 and 3 ) in the list, or deleted (Figure 2A, 3) from the list. The title of the Collection page, as well as the titles of the components themselves can also be edited in this view . Selecting Page Title (Figure 2A, part 5) pops up a dialog box (Figure 2B) to let the user enter a title for the collection that will appear as the page title for the new window containing the collection. The user can also double click on a Title to open another dialog box (Figure 2C) to let the user edit the component Title.The user presses the Submit link (Figure 2A, 4) to update the AURL with the latest revisions. The Collection List appears with the latest sorting and elements. The elements in the collection can be edited in another manner, referred to as Direct Manipulation" which we refer to below. First, we describe the Collection View, since Direct Manipulation takes place in the Collection View.
    [38" class="description-paragraph] (0038] Collection View. The list of components in the Collection View can be rendered in this embodiment as a Web page (the Collection View), which presents the complete text, images and links of the selected components in the order in which they appear in the list as shown in Figure 3. Figure 3, part 1, represents the Collection View of the selected element from Figure 4C. Note that each of the components in the Collection View uses the same font and layout style. The system also supports rendering each component with its original style and layout information. In this embodiment, we use Javascript's (Frames to support both stylistic versions of component views.
    [39" class="description-paragraph] [0039] Collections can also include image, sound, and other multimedia elements - indeed, any element that can be represented in a web page can be included in this embodiment of a collection.
    [40" class="description-paragraph] [0040] The components in the Collection View are each headed automatically by their associated Title value (Figure 3, part 2). Each component also automatically provides a link back to that component's source document (Figure 3, part 3). The collection page title displays the Title assigned it by the user (Figure 3, part 4).
    [41" class="description-paragraph] [0041] Rendering a collection (as represented in Fig 1-II) is initiated by clicking the "Preview" link in the Collection List window (Figure 2A, part 6).
    [42" class="description-paragraph] [0042] The following describes the details of one implementation behind Fig 1, II part 8: the request to preview sends the current AURL of the collection to the Java servlet "Collection.class." The Java servlet parses the AURL into smaller separate AURLs, each of which is an AURL of a component. Then it divides each AURL into its URL, XPath and Title as in the example above. As per Fig 1, II part 9, after the AURLparts have been parsed, the Java servlet downloads the XHTML documents from the different Web sites/pages and uses the XPath API to extract the components.5 Finally, as per Fig 1, II part 10, each component is collected as a Web page, and is then sent out to the client as the single Collection View Web page (Figure 3).5 There are two models for processing XML documents: the DOM (Document Object Model) and SAX (Simple APIfor XML). DOM provides a standard interface for working with an XML document in a tree hierarchy, whereas the SAX lets a program parse an XML document sequentially, based on an event handling model. Since a component of an XHTML document is a sub-tree of the tree hierarchy, our implementation uses the DOM model.
    [43" class="description-paragraph] [0043] Users can return to a web page and continue to add components to a collection and use the Collection List view at any time to re-render the collection or start a new collection. Users can also create collections of collections in the same way.
    [44" class="description-paragraph] [0044] Direct Manipulation Users may also manipulate the elements in a collection window directly: they may drag elements and resize them on the page, and then "submit" this state which creates a new AURL to represent the latest state of the collection. Direct manipulation is accomplished in this embodiment by utilizing the sizing and scrolling properties of the IFrames which hold the components displayed in a collection view. If the (Frame is resized from its default state, that information for that component is sent as part of the AURL. If the (Frame is moved on the page on its Layer from its default state, and the user chooses to save this new location, that information is also sent as an XYZ coordinate as part of the AURL once the user chooses to "submit" the new collection state.
    [45" class="description-paragraph] [0045] Users may also label a grouping of related elements. A border can be drawn around the components that are part of the group. This group name is also incorporated into the AURL. Finally, users may add short annotations to a group or collection element which can also be stored in the robust AURL, as per Figure 7B.
    [46" class="description-paragraph] [0046] An exemplary embodiment of the present invention has been described. This embodiment may be modified in many ways without departing the spirit and scope of the invention.
    权利要求:
    Claims I CLAIM:
    1. A method for collecting and managing within-page components and component collections as described herein.
    类似技术:
    公开号 | 公开日 | 专利标题
    US10706091B2|2020-07-07|User driven computerized selection, categorization, and layout of live content components
    US6822663B2|2004-11-23|Transform rule generator for web-based markup languages
    US7496839B2|2009-02-24|Template mechanism for document generation
    Asakawa et al.2000|Annotation-based transcoding for nonvisual web access
    US8001490B2|2011-08-16|System, method and computer program product for a content publisher for wireless devices
    US7080083B2|2006-07-18|Extensible stylesheet designs in visual graphic environments
    US7562287B1|2009-07-14|System, method and apparatus for selecting, displaying, managing, tracking and transferring access to content of web pages and other sources
    US6549220B1|2003-04-15|Method, system, and program for providing pages of information with navigation and content areas
    US20040205514A1|2004-10-14|Hyperlink preview utility and method
    US20060218492A1|2006-09-28|Copy and paste with citation attributes
    US20050203935A1|2005-09-15|Clipboard content and document metadata collection
    US20090094327A1|2009-04-09|Method and apparatus for mapping a site on a wide area network
    US20050198202A1|2005-09-08|Method for causing server to provide client computers with annotation functions for enabling users of the client computers to view object-based documents with annotations
    EP1146442A2|2001-10-17|Method and apparatus for storing and accessing electronic content
    US20130117663A1|2013-05-09|System and method for selectively displaying web page elements
    US20030135820A1|2003-07-17|Method of and a system for creating a button type bookmark in a web browser
    CA2363006C|2008-01-29|Document management method and tool
    WO2006137563A1|2006-12-28|Data processing device and data processing method
    WO2006137562A1|2006-12-28|Document processing device and document processing method
    US20020147847A1|2002-10-10|System and method for remotely collecting and displaying data
    US20070283251A1|2007-12-06|Web-based experience editor in a recursive browser system and uses thereof
    Maurer et al.2006|Transclusions in an html-based environment
    US20040177113A1|2004-09-09|Method, system, and article of manufacture for display of hierarchical data
    Hori et al.2004|Generating transformational annotation for web document adaptation: tool support and empirical evaluation
    CA2397873A1|2003-02-13|System and method for collecting and managing within-page components and component collections
    同族专利:
    公开号 | 公开日
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    法律状态:
    2005-08-12| FZDE| Dead|
    优先权:
    申请号 | 申请日 | 专利标题
    US31134101P| true| 2001-08-13|2001-08-13||
    US60/311,341||2001-08-13||
    [返回顶部]